Skip to content

Add timestamp to README#1960

Closed
hstaudacher wants to merge 1 commit intomainfrom
add-readme-timestamp
Closed

Add timestamp to README#1960
hstaudacher wants to merge 1 commit intomainfrom
add-readme-timestamp

Conversation

@hstaudacher
Copy link

Summary

  • Adds a "last updated" timestamp to the README for tracking purposes

Test plan

  • Verify the timestamp displays correctly in the README

🤖 Generated with Claude Code

This adds a "last updated" timestamp to the README for tracking purposes.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@hstaudacher hstaudacher requested a review from a team as a code owner February 4, 2026 16:45
Copilot AI review requested due to automatic review settings February 4, 2026 16:45
@hstaudacher
Copy link
Author

This was a test

@hstaudacher hstaudacher closed this Feb 4, 2026
@hstaudacher hstaudacher deleted the add-readme-timestamp branch February 4, 2026 16:46
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds a static "last updated" timestamp to the README.md file for tracking documentation freshness.

Changes:

  • Adds an italicized timestamp line (Last updated: 2026-02-04) near the top of README.md, positioned after the badge line and before the main heading

Comment on lines +3 to +4
*Last updated: 2026-02-04*

Copy link

Copilot AI Feb 4, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adding a static "last updated" timestamp to the README will require manual maintenance and will quickly become outdated. The README.md file is partially auto-generated by the script/generate-docs command (which regenerates sections between automated markers), but this script doesn't update timestamps. This means the timestamp will become inaccurate after the next documentation generation or any other README update.

Consider either:

  1. Removing the timestamp entirely (Git history already tracks when files were last modified)
  2. Implementing automatic timestamp generation in the generateReadmeDocs function in cmd/github-mcp-server/generate_docs.go so it stays current
  3. Using a CI workflow that automatically updates the timestamp on commits

If tracking documentation freshness is important, option 2 would be the most maintainable approach.

Suggested change
*Last updated: 2026-02-04*

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant